home *** CD-ROM | disk | FTP | other *** search
/ IRIX Base Documentation 2001 May / SGI IRIX Base Documentation 2001 May.iso / usr / share / catman / g_man / cat3 / OpenGL / glxbindhyperpipesgix.z / glxbindhyperpipesgix
Encoding:
Text File  |  2001-04-17  |  6.0 KB  |  133 lines

  1.  
  2.  
  3.  
  4. ggggllllXXXXBBBBiiiinnnnddddHHHHyyyyppppeeeerrrrppppiiiippppeeeeSSSSGGGGIIIIXXXX((((3333GGGG))))    OOOOppppeeeennnnGGGGLLLL RRRReeeeffffeeeerrrreeeennnncccceeee ---- GGGGLLLLXXXX    ggggllllXXXXBBBBiiiinnnnddddHHHHyyyyppppeeeerrrrppppiiiippppeeeeSSSSGGGGIIIIXXXX((((3333GGGG))))
  5.  
  6.  
  7.  
  8. NNNNAAAAMMMMEEEE
  9.      ggggllllXXXXBBBBiiiinnnnddddHHHHyyyyppppeeeerrrrppppiiiippppeeeeSSSSGGGGIIIIXXXX - bind a rendering context with a hyperpipe
  10.      configuration
  11.  
  12.  
  13. CCCC SSSSPPPPEEEECCCCIIIIFFFFIIIICCCCAAAATTTTIIIIOOOONNNN
  14.      int ggggllllXXXXBBBBiiiinnnnddddHHHHyyyyppppeeeerrrrppppiiiippppeeeeSSSSGGGGIIIIXXXX( Display *_d_p_y,
  15.                                int _h_p_I_d )
  16.  
  17.  
  18. PPPPAAAARRRRAAAAMMMMEEEETTTTEEEERRRRSSSS
  19.      _d_p_y   Specifies the connection to the X server.
  20.  
  21.  
  22.      _h_p_I_d  Specifies the hyperpipe id.
  23.  
  24.  
  25. DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  26.      ggggllllXXXXBBBBiiiinnnnddddHHHHyyyyppppeeeerrrrppppiiiippppeeeeSSSSGGGGIIIIXXXX is part of the SSSSGGGGIIIIXXXX____hhhhyyyyppppeeeerrrrppppiiiippppeeee extension.
  27.  
  28.      ggggllllXXXXBBBBiiiinnnnddddHHHHyyyyppppeeeerrrrppppiiiippppeeeeSSSSGGGGIIIIXXXX binds a rendering context to a hyperpipe,
  29.      establishing an association between the process, context and hyperpipe.
  30.      Every process participating in a hyperpipe should call
  31.      ggggllllXXXXBBBBiiiinnnnddddHHHHyyyyppppeeeerrrrppppiiiippppeeeeSSSSGGGGIIIIXXXX after creating and choosing a rendering context.
  32.      Hyperpipe requests to a process and its current context will not begin
  33.      until this call is made.
  34.  
  35.      _h_p_I_d must be a valid configured hyperpipe; else this call will fail.
  36.  
  37.      Calling ggggllllXXXXBBBBiiiinnnnddddHHHHyyyyppppeeeerrrrppppiiiippppeeeeSSSSGGGGIIIIXXXX with a value of -1, unbinds the rendering
  38.      context. If there is no current bound hyperpipe, calls to unbind are
  39.      ignored and no error is generated.
  40.  
  41.      ggggllllXXXXBBBBiiiinnnnddddHHHHyyyyppppeeeerrrrppppiiiippppeeeeSSSSGGGGIIIIXXXX works with a direct context only.
  42.  
  43.  
  44. RRRREEEETTTTUUUURRRRNNNN VVVVAAAALLLLUUUUEEEESSSS
  45.      Returns 0000 on success.
  46.  
  47.      Returns GGGGLLLLXXXX____BBBBAAAADDDD____HHHHYYYYPPPPEEEERRRRPPPPIIIIPPPPEEEE____SSSSGGGGIIIIXXXX if there is no valid hyperpipe
  48.      configuration corresponding to _h_p_I_d.
  49.  
  50.      Returns GGGGLLLLXXXX____BBBBAAAADDDD____CCCCOOOONNNNTTTTEEEEXXXXTTTT if there is no valid current rendering context.
  51.  
  52.  
  53. NNNNOOOOTTTTEEEESSSS
  54.      A process and context can bind to only one hyperpipe at any time.  If a
  55.      process calls ggggllllXXXXBBBBiiiinnnnddddHHHHyyyyppppeeeerrrrppppiiiippppeeeeSSSSGGGGIIIIXXXX more than once without an intervening
  56.      unbind, then the subsequent bind will fail and return
  57.      GLX_BAD_HYPERPIPE_SGIX.
  58.  
  59.      In the case of hyperpipes, it is valid to call glXSwapBuffers on a single
  60.  
  61.  
  62.  
  63.                                                                         PPPPaaaaggggeeee 1111
  64.  
  65.  
  66.  
  67.  
  68.  
  69.  
  70. ggggllllXXXXBBBBiiiinnnnddddHHHHyyyyppppeeeerrrrppppiiiippppeeeeSSSSGGGGIIIIXXXX((((3333GGGG))))    OOOOppppeeeennnnGGGGLLLL RRRReeeeffffeeeerrrreeeennnncccceeee ---- GGGGLLLLXXXX    ggggllllXXXXBBBBiiiinnnnddddHHHHyyyyppppeeeerrrrppppiiiippppeeeeSSSSGGGGIIIIXXXX((((3333GGGG))))
  71.  
  72.  
  73.  
  74.      buffered visual. glXSwapBuffers is the command that causes a hyperpipe to
  75.      switch to the next pipe as determined by the hyperpipe configuration.  In
  76.      order to call glXSwapBuffers successfully, a rendering context bound to a
  77.      hyperpipe should be associated with the drawable specified by
  78.      glXSwapBuffers.
  79.  
  80.      It is possible to determine if a context is associated with a hyperpipe
  81.      by calling glXQueryContextInfoEXT with the attribute
  82.      GLX_HYPERPIPE_ID_SGIX.
  83.  
  84.  
  85.  
  86. MMMMAAAACCCCHHHHIIIINNNNEEEE DDDDEEEEPPPPEEEENNNNDDDDEEEENNNNCCCCIIIIEEEESSSS
  87.      The GLX_SGIX_hyperpipe extension is currently supported only on
  88.      IR2/DPLEX.  The individual capabilities of each machine may differ.
  89.  
  90.  
  91. SSSSEEEEEEEE AAAALLLLSSSSOOOO
  92.      ggggllllXXXXQQQQuuuueeeerrrryyyyHHHHyyyyppppeeeerrrrppppiiiippppeeeeNNNNeeeettttwwwwoooorrrrkkkkSSSSGGGGIIIIXXXX ggggllllXXXXHHHHyyyyppppeeeerrrrppppiiiippppeeeeCCCCoooonnnnffffiiiiggggSSSSGGGGIIIIXXXX
  93.      ggggllllXXXXQQQQuuuueeeerrrryyyyHHHHyyyyppppeeeerrrrppppiiiippppeeeeCCCCoooonnnnffffiiiiggggSSSSGGGGIIIIXXXX ggggllllXXXXDDDDeeeessssttttrrrrooooyyyyHHHHyyyyppppeeeerrrrppppiiiippppeeeeCCCCoooonnnnffffiiiiggggSSSSGGGGIIIIXXXX hhhhyyyyppppeeeerrrrppppiiiippppeeee
  94.  
  95.  
  96.  
  97.  
  98.  
  99.  
  100.  
  101.  
  102.  
  103.  
  104.  
  105.  
  106.  
  107.  
  108.  
  109.  
  110.  
  111.  
  112.  
  113.  
  114.  
  115.  
  116.  
  117.  
  118.  
  119.  
  120.  
  121.  
  122.  
  123.  
  124.  
  125.  
  126.  
  127.  
  128.  
  129.                                                                         PPPPaaaaggggeeee 2222
  130.  
  131.  
  132.  
  133.